breaking: remove MediaPlaybackRequiresUserAction and update MediaTypesRequiringUserActionForPlayback to proper variable types #797
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation and Context
MediaPlaybackRequiresUserAction
was replaced withMediaTypesRequiringUserActionForPlayback
in a previous PR. Since theMediaTypesRequiringUserActionForPlayback
defaults will always exist indefaults.xml
,MediaPlaybackRequiresUserAction
will never be read. The old preference logic should actually be removed.Additionally, the old preference
MediaPlaybackRequiresUserAction
acceptedboolean
values but the newMediaTypesRequiringUserActionForPlayback
preference does not accept boolean. This needs to be corrected to accept proper value types.Description
This PR removes all of
MediaPlaybackRequiresUserAction
logic except for the deprecated warning. The warning is used to provide users a migration step. It will be removed in a later release.This PR has also updated the native code to pass in the correct variable types for the new
MediaTypesRequiringUserActionForPlayback
preference option.Example valid preference option with proper values are:
Testing
npm t
cordova platform add
cordova build ios
Checklist